Will someone please confirm of deny my observation that function "today()" returns the time on the DOORS server, not on the client. This works:
print dateAndTime(today) "\n"
llandale - Wed Feb 16 13:49:02 EST 2011 |
|
Re: today is server time? Doug.Zawacki - Tue Feb 22 23:45:19 EST 2011
Louie,
If you turn on the server monitor and run the function in a loop for, say 1000 times. You will see that it appears no communications appear to be going on with the server. Thus, I would conclude that it is the client date and time of today and NOT the server.
|
|
Re: today is server time? PDU - Wed Feb 23 01:51:57 EST 2011 Doug.Zawacki - Tue Feb 22 23:45:19 EST 2011
Louie,
If you turn on the server monitor and run the function in a loop for, say 1000 times. You will see that it appears no communications appear to be going on with the server. Thus, I would conclude that it is the client date and time of today and NOT the server.
Yes i confirm :
-
change the client date
-
execute print dateAndTime(today) "\n"
the date is the client date
Pierre
|
|
Re: today is server time? llandale - Wed Feb 23 09:22:36 EST 2011 PDU - Wed Feb 23 01:51:57 EST 2011
Yes i confirm :
-
change the client date
-
execute print dateAndTime(today) "\n"
the date is the client date
Pierre
OK. I can log into our server and noticed that its time is behind that of my client. running dateAndTime(today) seems to display 1.25 minute delay on the PC, so when my clock shows 8:21:30, dateAndTime(toda) shows 8:20:15. Turns out that was the same time within seconds as on the server. I see that when on the server, dateAndTime(today) is accurate to the second. Perhaps there is something odd with my client PC.
Anyway, indeed today() is client PC time; whereas the login history time is server time.
|
|